On one windows box, for sure, cookies were not set when using the header("Location: "); redirect. One fix was to generate a transition page with a <meta> refresh tag. Using the header("Refresh: 0; URL= "); solution is easier and cleaner. <img src="/forum/images/graemlins/smile.gif" alt="" /><br /><br />It was a windows machine causing the problem... go figure. <img src="/forum/images/graemlins/wink.gif" alt="" /><br /><br />Anyhow... the others that have reported this utility as not working were having problems on windows boxes. (I do believe they all were but I could be wrong)<br /><br /><br /><br />

Is "Refresh" a valid HTTP header? If not, shouldn't echo() or print() be used instead of header()?

As far as I can tell, no it's not specified. I found some limited discussions on it's use but only as options against header/Location. I'm still going over the specifications though. Perhaps there is an additional header that can be sent with Location to get the same affect?<br /><br />I'm also looking at the fact that no output is supposed to be sent before a header() call. This could be the reason the cookies are not being expired?<br /><br />I guess I'll keep going over this but for now the header/Refresh does seem to work. <img src="/forum/images/graemlins/smile.gif" alt="" />